perf: optimisation for date_part with seconds#23444
Open
theirix wants to merge 1 commit into
Open
Conversation
Contributor
|
run benchmark date_part |
|
🤖 Benchmark running (GKE) | trigger CPU Details (lscpu)Comparing perf-date_part-seconds (a68f33a) to 1e77af8 (merge-base) diff using: date_part File an issue against this benchmark runner |
|
🤖 Benchmark completed (GKE) | trigger Instance: CPU Details (lscpu)Details
Resource Usagedate_part — base (merge-base)
date_part — branch
File an issue against this benchmark runner |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
date_partUDF optimisations #23351.Rationale for this change
Benches were added recently in #23350 . Improve and measure some optimisations.
What changes are included in this PR?
seconds_nsandseconds_as_i32. A pretty rare code path.Are these changes tested?
Are there any user-facing changes?